home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr11
/
ibmlist.zip
/
TSEXPRES.CHA
< prev
Wrap
Text File
|
1990-12-12
|
40KB
|
771 lines
title: Common Fixed disk questions 1001
Q) Why do Format and some utilities say my fixed disk has 64
heads? Surely this isn't so!
A) The original PC BIOS only supported up to 1024 cylinders
(the counter is a 10-bit field). Many programs would crash
if this were increased to cope with today's much larger
disks. So the drive controller 'cheats' by pretending it has
more heads. This is OK as even the original PC BIOS had a 1-byte
counter for the number of heads (ie up to 256). The controller
itself translates the address BIOS sends to the 'real'
location on the disk. This ensures software compatibility.
NB. It also confuses certain benchmark programs, which report that ESDI
drives have much worse performance than is actually the case. Beware!
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) I thought the Model 70-121 had a 120M disk, but FDISK and
some utilities say I only have 115M. CHKDSK doesn't report
any bad sectors. Where is my missing 5 meg?
A) It depends how you define a 'megabyte'. When talking about
RAM for instance, it always means 1024*1024. However, when
referring to fixed disks it often means 1000*1000. Your disk
does have 120,000,000 bytes (more, in fact) which, as far as
the industry goes, can honestly be described as 120M.
Programs which report 115M are working on the 1024*1024
megabyte. If you work it out, 115*1024*1024 = 120,586,240.
A similar situation arises with the 320M SCSI drive, which may
show up as 304M or 305M (depending on how it is partitioned).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) I can't get the 60M upgrade to work on a Model 50. Please
advise.
A) You need two things - the 60M Option Diskette, and the
50/60 Reference Diskette 1.04. Earlier versions will not
work. You must then boot the Reference Diskette and select
"copy an option diskette" to add the 60M support.
Now run 'automatic configuration' and the drive should work.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) Can I install a 314M drive in a 60-071?
Q) Can I install a 60M drive in a 55SX-031?
Q) Can I install a 120M drive in a 70-M61
etc
A) To all the above is the same - yes it works, but no it isn't
supported. There are two considerations. Firstly, any warranty may
be invalidated by a 'roll-your-own' configuration. Secondly, not
all the parts are necessarily sold as upgrades. For example, the
only way to purchase a 120M drive is through IBM Sold Parts.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) I want to install a large (80M) non-IBM drive in a PC-AT, but this
only supports drive types 1 to 15. Is there a BIOS upgrade which
supports more? (The AT-X BIOS supports 1-47)
A) No - there is no AT BIOS upgrade, and indeed many of the drive types
above 23 are not actually implemented even on the AT-X.
It is possible (in theory) to support ANY drive on the AT. You need
to define a 'Fixed Disk Drive Parameter Table' and point interrupt
vector 41H (first drive) or 46H (second drive) at it.
See the 'BIOS Technical Reference' manual for details. IBM cannot
assist or support you with this.
~~~~~~
title: Common Diskette and Formatting Questions 1002
Q) Can I attach a 1.44M 3.5" diskette drive to a PC or AT?
A) No. The BIOS on these systems does not support 1.44M
drives, and there are no BIOS 'upgrades' to enable this.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) Can I attach a 1.2M 5.25" drive to a Model 30 or 30-286?
A) No. This drive requires an adapter which is only
available in Micro Channel format.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) I have a 3.5" 720K External drive attached to a PC-AT but
it doesn't work. What is wrong?
A) You need a device driver called EXDSKBIO.DRV in
CONFIG.SYS. This should be included with the drive.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) Can I install an internal 3.5" 720K drive in a PC-AT?
A) No. The internal drive is only supported in the AT-X and
XT-S.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) I have an external 3.5" drive on an AT but I get a lot of
formatting and read errors. Changing the drive doesn't help.
What is wrong?
A) The External drive seems rather prone to electromagnetic
interference from other devices. Place it as far as possible
from the system unit, display and printer.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) I'm confused as to what drives I can attach to the P70.
Please explain.
A) The old 360K 5.25" drive (p/n 6134350) can attach directly
to the 'external device port' using cable p/n 23F2716. No
adapter is needed. However the 1.2M 5.25" drive cannot be
attached in this way - you need adapter 6451007 (but not the
cable).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) How do I attach a 360K external drive to a 30-286?
A) You need cable p/n 27F4245, as well as the drive and adapter. Note
that this cable fits onto the system-board, and the original cable is
moved to the 'middle' connector of 27F4245. The other end attaches to
the 360K adapter.
------------------------------------------------------------
Q) We did not receive a cable or 'dummy drive' with the 1.2M
adapter 6451007. How do we connect it up?
A) Unlike the old 360K adapter (6450245) the 1.2M adapter
does not attach to the B: drive connector. There is a
connector on the card which looks just like the one on the
old card, but this is for attachment of an Internal 5.25"
drive. The adapter itself just plugs in - no cables are
needed.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) I can format diskettes OK singly, but when I try to 'format another'
it always fails with a 'bad track 0' error.
A) If you have a Model 50, 60 or early 80 you must install the
DASDDRVR.SYS fix (described elsewhere in Infosearch). A similar problem
also exists on the 70-A21 if you are using DOS 3.3, which is fixed by
the latest DASDDRVR.SYS only (Reference Diskette 1.10 or later).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Q) Why is there so much difference between the unformatted and
formatted capacity of a diskette? Where does 600K go on a '2M'
diskette?
A) Every track on the diskette has a track ID field. Every sector on
each track has a sector ID field. Every field also has a length and
CRC-check field. Every field is separated by a gap. All this control
information is required by the controller circuitry to find and read
the data reliably. In addition, some space is used by the boot sector,
the File Allocation Tables, and the root directory.
The unformatted capacity includes all space used by the control fields,
inter-record gaps and DOS areas. The formatted capacity gives the
space available for user data.
~~~~~~~~~
title: SCSI Performance Considerations 1003
Q1) IBM claim an 12.5ms average access time for the 320M SCSI drive
but I've run several benchbark programs which report much slower
speed than this
Q2) Even allowing for benchmark errors, I have several real live
applications which seem slower (certainly no faster) on a SCSI
system, whereas I'd expected a considerable performance boost.
Answer..........:
A1) Average-access benchmarks issue many seek commands to known track
addresses then average the time taken. This technique simply won't
work accurately on SCSI drives.
(a) SCSI remaps the track/sector address as seen by BIOS to a relative
block address. What BIOS (and the benchmark) thinks are adjacent
tracks probably are not really adjacent on the disk
(b) The 12.5ms time is that measured at the drive. This does not
include the time taken to parse the command, set up the adapter and
initialise the SCSI bus, then the time taken for the adapter to
tell the system when the command is complete
(c) Most importantly, the SCSI adapter will not permit multiple seek
commands without an intervening disk read or write. This is to
protect the voice-coil actuator from overheating. This is quite
reasonable as in real usage you would never issue a seek without
a subsequent I/O. The adapter will force a wait period between
consecutive seeks to allow the actuator to cool.
A2) This depends on the application. Remember that SCSI is designed to
be a general purpose interface. As such there is much more protocol
and 'handshaking' required to setup the disk before I/O begins than
with ST506 or ESDI. Once transfer does begin however, SCSI has a
much faster I/O data rate. This means that transfer of small files
may be slower, but large files (16K or more) will transfer more
quickly overall.
Another factor is that the SCSI adapter will queue requests
briefly in case a subsequent request arrives. This enables it to
process multiple I/O requests with the minimum of head movement
giving an OVERALL performance improvement though INDIVIDUAL
requests may be delayed slightly. This is particularly beneficial
in multi-tasking applications and/or LAN servers.
Finally, do not use the INSTDBUF fix unless you absolutely have to,
since this can result in a 20% performance degradation.
~~~~~~~
title: Display specifications 1004
IBM DISPLAY SUMMARY
║ Number ║Screen ║Dot ║Video ║ Horiz ║Refresh║ Resolution ║
║ of ║ Size ║Pitch ║Bandw ║ Freq. ║Rate ║ choices ║
║ Colours ║ (in.) ║(mm) ║(MHz) ║ (KHz) ║(Hz) ║ ║
-----------------------------------------------------------------------
Mono ║ (4) ║ 11.5 ║ n/a ║ 16.3 ║ 18.4 ║ 60 ║ 720 x 350 ║
Colour ║ 16 ║ 13 ║ 0.43 ║ 14.3 ║ 15.75 ║ 60 ║ 640 x 200 ║
Base ║ 16 ║ 13 ║ 0.63 ║ 14.3 ║ 15.75 ║ 60 ║ 640 x 200 ║
Enhanced║ 64 ║ 13 ║ 0.31 ║ 14.3 ║ 15.75 ║ 60 ║ 640 x 200 ║
║ ║ ║ ║ 16.3 ║ 21.8 ║ 60 ║ 720 x 350 ║
Prof'nl ║ 256 ║ 13 ║ 0.28 ║ 25 ║ 30.48 ║ 60 ║ 640 x 480 ║
8503 ║ 64 grey║ 12 ║ n/a ║ 25 ║ 31.5 ║ 70 ║ 720 x 400 ║
║ ║ ║ ║ ║ ║ 60 ║ 640 x 480 ║
8506 (#)║ 16 grey║ 17 ║ n/a ║ ║ 50 ║ 71 ║ 736 x 362 ║
║ (portrait) ║ ║ 50 ║ 71 ║ 736 x 414 ║
║ ║ ║ ║ ║ 50 ║ 70 ║ 656 x 496 ║
║ ║ ║ ║ ║ 50 ║ 40* ║ 850 x 1200 ║
8508 (#)║ 16 grey║ 19 ║ n/a ║ ║ 71 ║ 93 ║ 736 x 724 ║
║ ║ ║ ║ ║ 71 ║ 82 ║ 736 x 828 ║
║ ║ ║ ║ ║ 71 ║ 67 ║ 1360 x 1024 ║
║ ║ ║ ║ ║ 62 ║ 49* ║ 1600 x 1200 ║
8512 ║ 256K ║ 14 ║ 0.41 ║ 25 ║ 31.5 ║ 70 ║ 720 x 400 ║
║ ║ (stripe) ║ ║ 60 ║ 640 x 480 ║
8513 ║ 256K ║ 12 ║ 0.28 ║ 25 ║ 31.5 ║ 70 ║ 720 x 400 ║
║ ║ ║ ║ ║ ║ 60 ║ 640 x 480 ║
8514 ║ 256K ║ 16 ║ 0.31 ║ 28 ║ 31.5 ║ 70 ║ 720 x 400 ║
║ ║ ║ ║ 25 ║ 31.5 ║ 60 ║ 640 x 480 ║
║ ║ ║ ║ 45 ║ 35.5 ║ 43.5* ║ 1024 x 768 ║
8515 ║ 256K ║ 14 ║ 0.28 ║ 28 ║ 31.5 ║ 70 ║ 720 x 400 ║
║ ║ ║ ║ 25 ║ 31.5 ║ 60 ║ 640 x 480 ║
║ ║ ║ ║ 45 ║ 35.5 ║ 43.5* ║ 1024 x 768 ║
* = interlaced (all others non-interlaced)
# = supported with Image Adapter/A and Image Plus only
~~~~~~~~
title: SCSI Switch Settings 1005
SCSI drive switch settings
--------------------------
SCSI device switches MUST be correctly set if the SCSI subsystem is
to work properly. The following documents the switch settings for IBM
SCSI fixed disks. It is also important that devices at each end of the
SCSI bus are terminated, but others have their terminators removed.
----------------------------------------------------------------------
For 60 and 120 Mb files -
Looking at the file with SCSI connector pointing away from you,
there is a set of four DIP switches. The DIP switches are as follows:
-------------------------------
| SCSI connector |
-------------------------------
-----------------
| 1 | 2 | 3 | 4 |
-----------------
Switches 1,2,3 are for SCSI address ID and are set as follows
(On = switch down on SCSI connector side of switch)
SCSI ID switch
6 3,2 On 1 Off
5 3,1 On 2 Off
4 3 On 2,1 Off
3 2,1 On 3 Off
2 2 On 3,1 Off
1 1 On 3,2 Off
0 3,2,1 Off
For the 320 Mb file, the SCSI ID is set with jumpers located on the
back of the drive. Looking at the back of the drive with the SCSI
connector on the top, the jumpers are as follows:
---------------------
| 1 | 2 | 3 | 4 | 5 |
---------------------
Jumpers 1,2 and 3 are used for SCSI ID selection
SCSI ID Jumper
6 3,2 On 1 Off
5 3,1 On 2 Off
4 3 On 2,1 Off
3 2,1 On 3 Off
2 2 On 3,1 Off
1 1 On 3,2 Off
0 3,2,1 Off
~~~~~~~~~~~~
title: CTSL SUPPORT PROCEDURES 1006
IBM Authorised Dealer Guide to CTSL
-----------------------------------
Several PC and PS/2 software products available through the Dealer channel
are now fully supported by IBM Software Customer Engineering.
Products are designated as CTSL when they are announced and you should
refer to the annoucement material to see which products are so defined.
CE Software Support Centre Service Areas
----------------------------------------
BASINGSTOKE 0256-818888
Bedfordshire Essex Norfolk
Berkshire Greater London
Northamptonshire
Buckinghamshire Hampshire Oxfordshire
Cambridgeshire Hertfordshire Suffolk
Channel Islands Isle of Wight Surrey
Dorset Kent West Sussex
East Sussex
BIRMINGHAM 021-454-9000
The rest of England
plus:
Scotland
Northern Ireland
Wales
Software Update Procedure
-------------------------
From time to time, Corrective Service Diskettes (CSDs) are made
available for CTSL products. You will normally be made aware of these
via DialIBM, however, downloading several high density diskette images
over a dial-up line can be fraught with problems. You can obtain
these CSDs from the IBM Software Customer Engineering (S/W CE) Support
Group for your area by telephoning them, giving them your Dealer CTSL
Registration Number, and identifying which CSD you require.
Defect Reporting Procedure
--------------------------
If you suspect a defect in a CTSL designated product, you should use
the normal DialIBM facilities to investigate your problem and, if
necessary, submit a problem to the appropriate EC specialist. If your
suspicions are proved to be correct then your problem will be
transferred to the IBM S/W CE Support Group for your area. The CE S/W
Support Centre Call Receipt Desk will open a Problem Management Record
(PMR) for the problem, which will have a unique number.
The caller will need to give the Dealers CTSL Registration Number,
confirm or correct the Dealer Contact Name, Telephone Number and
Extension, and give a summary of the problem.
The PMR will then be placed on a queue for the appropriate CE S/W
Support Centre specialist who will call the Dealer back to progress
the problem. Any relevant documentation collected by the DM specialist
will be forwarded to the CE S/W Support Centre specialist to be
appended to the PMR. If you are absolutely certain that you have
identified a defect in a CTSL designated product and can find no
details of a fix or bypass from DialIBM, you can call the IBM S/W CE
Support Group for your area to register your problem directly and
provide the information outlined above.
If your problem is subsequently found to be a non-defect then it
will be referred back to the EC Technical Support Group for attention
via DialIBM.
How to find your CTSL Registration Number
-----------------------------------------
This is not the Dealer Number which you normally use when calling EC
Technical Support but an IBM Customer Number used when ordering
products from IBM. Your Account Administrator will be able to tell
you your Outlet's CTSL Registration number.
Remember - without a valid CTSL Registration Number you will not
receive CSDs on request or defect support for CTSL designated
products.
~~~~~~~~~
~~~~~~~~~~~~
title: EMS Configuration 1007
EMS/LIM Memory emulation PC and PS/2 systems
System Requirements (see below)
------ ------------------------
XT-S (1) or (2)
XT-286 (3)
AT, AT-X (1) or (2) or (3)
PS/2 Model 30 (1) or (2)
PS/2 Model 30-286 (4)
PS/2 50, 50Z or 60 (5) or (6) or (7) or (10)
PS/2 55SX (10) or (11)
PS/2 70, P70 or 80 (8) or (9)
Hardware EMS Driver EMS Level
------------ ---------- ---------
(1) XMA 3270 WSP 3.2
(2) XMA DOS 4.0 4.0
(3) 512K/2M Above Disc 4.0
(4) Planar or Multifunction Adapter Above Disc 4.0
(5) XMA/A * 3.2
(6) XMA/A or 1-2M DOS 4.0 4.0
(7) Planar over 640K, XMA/A or 1-2M, Above Disc 4.0
(8) Any (planar or adapter) 3270 WSP 1.1 3.2
(9) Any (planar or adapter) DOS 4.0 4.0
(10) 80286 2-8M * (See Note) 4.0
(11) Planar over 640K DOS 4.0 4.0
--------------------------------------------------------------
* EMS driver included on Option Diskette with adapter.
NB. Also see EMS-RULES for driver and DOS-version information.
--------------------------------------------------------------
Part numbers:-
XMA = 2685193 512K/2M = 6450343 Multifunction = 30F5348
1-2M = 6451001 XMA/A = 1497252 (2M) or 1497259 (0-8M)
80286 2-8M = 6450609 Above Disc = 38F3036
80386 memory adapters: 2-6M = 6450367
2-8M = 6450605
2-16M = 34F3077
4-16M = 34F3011
~~~~~~~~~~
title: PS-2 TRAP ERRORS 1008
================
THIS TIP HAS BEEN GENERATED TO GUIDE THE SERVICER THROUGH.
THE VARIOUS TRAP ERRORS THAT CAN OCCUR ON PS-2.
IT SHOULD BE USED ONLY AS A GUIDE AND DOES NOT COVER ALL
TRAP ERRORS THAT COULD OCCUR
THE TIP IS IN TWO SECTIONS
A. GATHERING INFORMATION and B. TABLE OF TRAP NUMBER AND
POSSIBLE CAUSE or ACTION TO BE TAKEN.
SECTION A GATHERING INFORMATION ABOUT THE TRAP
THE FOLLOWING INFORMATION WILL BE REQUIRED BY YOU TO GET YOU
TO THE CORRECT POSITION IN THE TABLE IN SECTION B AND WILL
CERTAINLY BE REQUIRED BY YOUR SUPPORT IF IT IS NECESSARY TO
OPEN A PMR (PMH or PMS)
1. WHICH TRAP ERROR(S)? 0002
0006
0007 etc
**** IF ONE TRAP ERROR IS FOLLOWED BY ANOTHER THEN THE
FOLLOWING ANSWERS ARE REQUIRED FOR BOTH TRAPS
2. WHAT IS THE FULL ERROR DISPLAYED ON THE SCREEN?
INCLUDE
ALL REGISTERS DISPLAYED
THE MESSAGE AT THE BOTTOM OF THE SCREEN
eg HARDWARE MEMORY ERROR AT LOCATION XXXX,YYYY
HARDWARE ERROR ON LOCATION CARD
INTERNAL PROCESSING ERROR AT LOCATION XXXX,YYYY
ETC ETC
3. HOW DOES THE CUSTOMER RECOVER ? HAVE ALL OPTIONS BEEN TRIED?
eg POWER OFF/ON ?
CTRL + ALT + DEL ?
PRESSING ANY KEY or KEYS.... NOTE ANY RESULTING MESSAGE
4. WHAT IS THE HARDWARE CONFIGURATION ?
INCLUDE ADAPTERS INSTALLED
WHICH SLOTS THE ADAPTERS ARE IN
TOTAL MEMORY INSTALLED
PS-2 MODEL AND TYPE ie 85XX-ZZZ
ANY OEM CARDS AND THEIR SLOTS
ETC ETC
**** IF IN ANY DOUBT VIEW THE CONFIGURATION BY RUNNING
THE REFERENCE DISKETTE AND THEN DO SCREEN PRINTS
5. WHAT IS THE SYSTEM CONFIGURATION
INCLUDE
TYPE OF LAN
NUMBER OF MACHINES ON LAN
THE SOFTWARE BEING USED TO RUN THE LAN
ETC ETC
6. WHAT IS THE SOFTWARE CONFIGURATION ?
INCLUDE
VERSION OF OPERATING SYSTEM (OS2, DOS etc)
CSD LEVEL (TYPE 'SYSLEVEL' at C> PROMPT)
OTHER SOFTWARE(S) and VERSION(S)
7. CAN THE CUSTOMER REPRODUCE THE PROBLEM AT WILL ?
IF YES HAVE AN EXACT UNDERSTANDING OF HOW IT IS DONE.
8. WHAT WERE THE SEQUENCE OF EVENTS PRIOR TO THE ERROR.
9. WHAT WAS HAPPENING / CUSTOMER DOING AT TIME OF ERROR.
10.ANY RECENT CHANGES, or OTHER RELEVANT INFORMATION
EG THIS IS A NEW INSTALL.
RECENTLY ADDED EXTRA MEMORY/ADAPTER TO MACHINE
RECENTLY ADDED LATEST LEVEL OF CSD
RECENTLY PUT NEW SOFTWARE ON
NUMBER OF REQUESTERS ASSOCIATED WITH THE SERVER
ETC ETC
11. SIZE OF THE PROBLEM FROM THE CUSTOMER VIEW ?
NUMBER OF MACHINES AFFECTED
SEVERITY OF IMPACT
POTENTIAL FUTURE IMPACT TO CUSTOMER'S and IBM'S
BUSINESS
SECTION B
---------------------------------------------------------------
║ TRAP ║ SYSTEM ║ ACTIONS ║
---------------------------------------------------------------
║ ║ ║ WITH MESSAGE 'EXCEPTION IN DEVICE DRIVER ' ║
║ 0002 ║ ALL ║ 1. REFER TO TIP H037481 ║
║ ║ ║ 2. RUN CHKDSK /F- REPAIR ANY CORRUPT FILE(S)║
║ ║ ║ 3. RAISE PMR (PMH) ║
--------------------------------------------------------------
║ ║ ALL ║ OCCURS WITH T/R INSTALLED AND WHEN ║
║ 0002 ║only on ║ INITIALISING THE LAN AT IPL ║
║ ║ IPL ║ 1. INSTALL LATEST TRNETDD.SYS (APAR JR02045)║
║ ║ ║ 2. CHECK ALL H/W MEMORY PER TIP H045006 ║
║ ║ ║ 3. RAISE PMR (PMH) ║
--------------------------------------------------------------
║ ║ ║ WITH ALL OTHER MESSAGES ║
║ 0002 ║ ALL ║ 1. WITH 113 ERRORS.. REFER TO TIP H064377 ║
║ ║ ║ 2. CHECK ALL H/W MEMORY PER TIP H045006 ║
║ ║ ║ 3. RUN CHKDSK /F- REPAIR ANY CORRUPT FILE(S)║
║ ║ ║ 4. RAISE PMR (PMH) ║
---------------------------------------------------------------
---------------------------------------------------------------
║ ║ ║ 1. CHECK ALL H/W MEMORY PER TIP H045006 ║
║ 0006 ║ ALL ║ 2. RUN CHKDSK /F- REPAIR ANY CORRUPT FILE(S)║
║ ║ ║ 3. RAISE PMR (PMH and PMS) ║
║ ║ ║ 4. OEM S/W - IF YES CONTACT VENDOR ║
║-------------------------------------------------------------║
║-------------------------------------------------------------║
║ ║ ║ 1. RUN CHKDSK /F- REPAIR ANY CORRUPT FILE(S)║
║ 0007 ║ ALL ║ 2. RAISE PMR (PMS) ║
║ ║ ║ 3. OEM S/W - IF YES CONTACT VENDOR ║
║-------------------------------------------------------------║
║-------------------------------------------------------------║
║ ║ ║ 1. CHECK ALL H/W MEMORY PER TIP H045006 ║
║ 0008 ║ ALL ║ 2. RUN CHKDSK /F -REPAIR ANY CORRUPT FILE(S)║
║ ║ ║ 3. RAISE PMR (PMH and PMS) ║
║ ║ ║ 4. OEM S/W - IF YES CONTACT VENDOR ║
║-------------------------------------------------------------║
║ ║ ║ WITH THE MSG ║
║ ║ ║ 'SYS1942: A PROGRAM ATTEMPTED TO REFERENCE ║
║ ║ ║ STORAGE OUTSIDE THE LIMITS OF A STACK ║
║ 000C ║ ALL ║ SEGMENT' ║
║ ║ ║ -- INDICATES A STACK OVERFLOW OCCURRED IN ║
║ ║ ║ USER WRITTEN CODE OR APPLICATION ║
║ ║ ║ 1. CONTACT SOFTWARE SUPPORT ║
║ ║ ║ 2. RAISE PMR (PMS) ║
║-------------------------------------------------------------║
║ ║ ║ WITH THE MSG ║
║ 000C ║ ALL ║ 'EXCEPTION IN DEVICE DRIVER' ║
║ ║ ║ 1. REFER TO TIP H037481 ║
║ ║ ║ 2. RUN CHKDSK /F -REPAIR ANY CORRUPT FILE(S)║
║-------------------------------------------------------------║
║ ║ ║ WITH ALL OTHER MSGs ║
║ ║ ║ 1. WITH 113 ERRORS .. REFER TO TIP H064377 ║
║ 000C ║ ALL ║ 2. CHECK ALL H/W MEMORY PER TIP H045006 ║
║ ║ ║ 3. RUN CHKDSK /F -REPAIR ANY CORRUPT FILE(S)║
║ ║ ║ 4. RAISE PMR (PMS) ║
║-------------------------------------------------------------║
║-------------------------------------------------------------║
║ ║ ║ WITH THE MSG ║
║ ║ ║ 'SYS1943: A PROGRAM CAUSED A PROTECTION ║
║ ║ ║ VIOLATION ║
║ 000D ║ ALL ║ - MSG MAY INCLUDE NAME OF PROGRAM THAT ║
║ ║ ║ CAUSES ERROR ║
║ ║ ║ - INDICATES A GENERAL S/W ERROR IN EITHER ║
║ ║ ║ USER WRITTEN CODE,APPLICATION OR OS/2 ║
║ ║ ║ 1. CONTACT SOFTWARE SUPPORT ║
║ ║ ║ 2. RAISE PMR (PMS) ║
║-------------------------------------------------------------║
║ ║ ║ WITH THE MSG ║
║ ║ ║ 'INTERNAL PROCESSING ERROR OCCURED ║
║ 000D ║ ALL ║ AT 0220:3557' ║
║ ║ ║ 1. SET T/R RAM MEMORY WINDOW TO 16K ║
║ ║ ║ REF TIP H052921 AND H053510. ║
║ ║ ║ 2. INSTALL LATEST TRNETDD.SYS (APAR JR01657)║
║ ║ ║ 3. RAISE PMH (PMS) ║
║-------------------------------------------------------------║
║ ║ ║ DOUBLE TRAP 000D WITH THE MESG ║
║ ║ ║ 'INTERNAL PROCESSING ERROR OCCURRED ║
║ 000D/║ ALL ║ AT 0220:3557' ║
║ 000D ║ ║ 1. INSTALL LATEST NETBDD and ASCNETB ║
║ ║ ║ MODULES (APAR IC00096) ║
║ ║ ║ 2. RAISE PMR (PMS) ║
║-------------------------------------------------------------║
║ ║ ║ 1. WITH 113 ERRORS...REFER TO TIP H064377 ║
║ ║8570-A21║ 2. CHECK ALL H/W MEMORY PER TIP H045006 ║
║ 000D ║ ONLY ║ 3. CHECK SYSTEM BOARD LEVEL PER TIP H045006 ║
║ ║ ║ 4. RUN CHKDSK /F -REPAIR ANY CORRUPT FILE(S)║
║ ║ ║ 5. RAISE PMR (PMH and PMS) ║
║ ║ ║ 6. OEM S/W - IF YES CONTACT VENDOR ║
║-------------------------------------------------------------║
║ ║ ║ WITH ALL OTHER MSGs ║
║ ║ ALL ║ 1. With 113 ERRORS ...REFER TO TIP H064377 ║
║ ║ EXCEPT ║ 2. CHECK ALL H/W MEMORY PER TIP H045006 ║
║ 000D ║8570-A21║ 3. RUN CHKDSK /F -REPAIR ANY CORRUPT FILE(S)║
║ ║ ║ 4. RAISE PMR (PMH and PMS) ║
║ ║ ║ 5. OEM S/W - IF YES CONTACT VENDOR ║
--------------------------------------------------------------
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tip number: H053510
TRAP 000D INTERNAL PROCESSOR ERROR
==================================
SYMPTOM:PS/2 with 16/4 Token Ring adapter installed may fail
with "Trap 000D internal processor error message"This may happen
if the PS/2 is running OS/2 and the hardware reference disk set
the T-R ram memory window to 32K.Comms manager requires this to
be set to 16K.
Use the reference diskette to manually change the RAM size
to 16K avoiding conflicts with other adapters.This problem
should not give a TRAP 000D message and will be changed in a
later OS/2 EE 1.2 CSD (Refer to APAR JR01657 for software
solution).
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tip number: H052921
OS/2 LAN"RECEIVE BUFFER MEMORY ERROR
====================================
PS/2 with 16/4 Token Ring adapter installed may fail
at time of starting the OS/2 LAN requestor with the message
"Receive buffer memory error".
Use the Hardware Reference diskette (VIEW CONFIG.) to
check the Token Ring RAM Memory Window setting.
If this is set to 8K it must be manually reset to 16K for use
with the OS/2 Comms Manager.
If AUTOCONFIG. is run after the Token Ring RAM Memory window
has been manually reset it may be changed,even if a SAVE CONFIG
was executed.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tip number: H037481
ENHANCED 80386 MEMORY ADAPTER W/SYSTEM DETECTED MEMORY ERROR
============================================================
SYMPTOM: AN OPERATING SYSTEM DETECTED MEMORY ERROR, SUCH AS TRAP
0002 AND/OR 000C, MAY OCCUR IN THE FOLLOWING CONFIGURATION:
:
8580 MODEL 111 OR 311 RUNNING OS/2 SE OR EE,
AND AN ENHANCED 80386 MEMORY EXPANSION ADAPTER
LOCATED IN MICROCHANNEL SLOT #1.
:
THE ENHANCED 80386 MEMORY EXPANSION ADAPTER CAN BE IDENTIFIED BY
HAVING 3 SIMM CONNECTORS ON THE LEFT HALF OF THE ADAPTER AND ONE
SIMM CONNECTOR ON THE TOP RIGHT HALF OF THE ADAPTER.
ALL SYSTEM AND MEMORY DIAGNOSTICS AND THE ENHANCED
80386 MEMORY EXPANSION OPTION (OPTION # 33F3077,
FRU P/N34F2825) DIAGNOSTICS RUN ERROR-FREE.
MOVE THE 80386 ENHANCED MEMORY ADAPTER TO MICROCHANNEL I/O
SLOT #4.
IF MOVING THE ENHANCED MEMORY ADAPTER TO SLOT 4 OF THE SYSTEM
BOARD DOES NOT CORRECT THE PROBLEM, VERIFY THAT THE
ENHANCED 80386 MEMORY EXPANSION ADAPTER HAS RESISTORS POSITIONED
DIAGONALLY ACROSS MODULES U21, U22, U23 AND U24. IF THESE
RESISTORS ARE NOT PRESENT, REPLACE THE ADAPTER (FRU P/N34F2825).
REFER TO TIP H037846 UNDER FOR ADDITIONAL INFORMATION
IF REQUIRED.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tip number: H045006
IDENTIFICATION OF MEMORY & OS/2 TRAPS
=====================================
A NUMBER OF PROBLEMS HAVE BEEN REPORTED REGARDING TRAP ERRORS
UNDER OS/2.
SOME OF THESE HAVE BEEN CAUSED BY INCORRECT MEMORY BEING USED.
THE TABLE BELOW GIVES THE MANUFACTURING P/Ns,RESISTORS PRESENT
AT TOP RIGHT (IBM MANUFACTURED) OR MANUFACTURER CODE MARKINGS
ON THE SIMM CASING MADE BY THE MANUFACTURER (OEM) FOR THE
DIFFERENT SPEEDS AND SYSTEMS WHERE USED.
eg in table below
P/N23F9779 is the IBM Manufactured 100 NS MEMORY and is
recognised by the R1 and R2 Resistors at the top right.
P/N68X6254 is the OEM manufactured equivalent and has one
of the markings. Either can be used in the 8570 16MHZ or
8555.
_____________________________________________________________
║PART NUMBER ║ SPEED ║ MARKINGS ║ WHERE USED ║
║------------║-------║-----------------------║--------------║
║23F9779(IBM)║ 100 ║R1 AND R2 RESISTORS ║ 8570 16MHZ ║
║............║ ║.......................║ ║
║68X6254(OEM)║ ║ MSC2321-10YS18A ║ AND ║
║ ║ ║ HB56D512361B-10 ║ ║
║ ║ ║ MH51236AJ-10 ║ 8555 ║
║ ║ ║ ZA3617 ║ ║
║ ║ ║ THM265102S-10 ║ ║
║------------║-------║-----------------------║--------------║
║65X6249(IBM)║ 85 ║ ONLY R1 RESISTOR ║ 8570 20MHZ ║
║............║ ║.......................║ 8555 ║
║68X6127(OEM)║ ║ MNB36512S85 ║ 8570 16MHZ ║
║ ║ ║ THM365120S-85 ║ OPTION ║
║ ║ ║ MSC2321-85YS18A ║ 6450605/9 ║
║ ║ ║ HB56D512361B-8 ║ ║
║------------║-------║-----------------------║--------------║
║68X5806(IBM)║ 80 ║ ONLY R2 RESISTOR ║8570-A21 ║
║ ║ ║ ║8570-R21 ║
║____________║_______║_______________________║______________║
THE FOLLOWING PROCEDURE SHOULD BE USED AS A GUIDE TO OS/2 TRAP
ERROR DIAGNOSIS
D/T8580 TRAP 0002 and TRAP 000C.
THESE CAN BE CAUSED BY A
MIXTURE OF 80ns and 85ns MEMORY CHIPS WITHIN AN ADAPTOR or
ON THE SYSTEM BOARD. THE MEMORY EXPANSION CARD SHOULD BE MOVED
FROM SLOT 1 TO SLOT 4 (PREFERRED). A SECOND MEMORY EXPANSION
CARD SHOULD BE IN SLOT 2.
D/T8580 TRAP 000D
IF YOU GET THIS ERROR USING REFERENCE DISKETTE VER 1.10
TRY USING REFERENCE DISKETTE VER 1.06
D/T8570 TRAP 000D
THIS CAN BE FIXED BY FITTING A NEW LEVEL SYSTEM BOARD P/N15F7657
MUST BE AT MANUFACTURING LEVEL 64F1389. THE PROCESSOR CARD
SHOULD BE 15F7659 WITH MANUFACTURING P/N33F9901
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tip number: H064377
113 ERROR / SYSTEM HALT
=======================
PURPOSE: TO PROVIDE INSTRUCTIONS TO DETERMINE IF THE 60MB OR
120MB FIXED DISK SHOULD BE REPLACED TO CORRECT A 113 ERROR /
SYSTEM HALT IN AN 8550, 8555, 8570 OR 8573.
IDENTIFY AFFECTED FIXED DISK BY LOCATING A LABEL
ON THE FIXED DISK MARKED WITH EC A79678. ONLY FIXED DISKS THAT
MEET THE CONDITIONS DESCRIBED IN THE DETAIL BELOW SHOULD BE
REPLACED.
++++++++++++++++++++++++++++++++++++++++++++
AFFECTED MACHINES INCLUDE:
TYPE-MOD FDISK FRU P/N EC LABEL
8550-021 (OPT) 60MB 90X8627 A79678
8550-031 (OPT) 60MB 90X8627 A79678
8550-061 60MB 90X8627 A79678
8555-061 60MB 6128272 A79678
8570-A21 120MB 90X9286 A79678
8570-E61 60MB 90X8627 A79678
8570-121 120MB 90X9286 A79678
8573-061 60MB 90X8627 A79678
8573-121 120MB 90X9286 A79678
+++++++++++++++++++++++++++++++++++++++++++++
CERTAIN FIXED DISKS MAY CAUSE A 113 (DMA TIMEOUT) ERROR
/ SYSTEM HALT WHEN THE FIXED DISK AND OTHER DEVICES PERFORM
CONCURRENT OPERATIONS IN A MULTITASKING ENVIRONMENT. WHEN THIS
CONDITION OCCURS THE SYSTEM HALTS AND/OR DISPLAYS A DMA TIMEOUT
ERROR MESSAGE APPROPRIATE FOR THE OPERATING SYSTEM BEING USED.
THERE IS NO DATA LOSS FROM THIS CONDITION. TO RESTART, THE
SYSTEM MUST BE POWERED OFF THEN BACK ON. IF THE ABOVE CONDITION
EXISTS AND THE FIXED DISK MATCHES THE "PHYSICAL CHECK", REPLACE
THE FIXED DISK.
SOME EXAMPLES OF MULTI-TASKING SYSTEMS ARE: OS/2, AIX,
XENIX, AND TAPE BACKUP ROUTINES THAT RUN ON DOS OR A MULTI-
TASKING OPERATING SYSTEM.
SOME EXAMPLES OF SYSTEM HALTS ARE NON-MASKABLE INTERUP
ERRORS ( NMI ), 113 DIRECT MEMORY ACCESS ( DMA) ERRORS,
ORDER PARTS THROUGH NORMAL DISTRIBUTION. ALL AFFECTED
FIXED DISKS SHOULD BE RETURNED TO IBM.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tip number: H037846
SYSTEM LOCKS UP WITH 110 ERROR OR TRAP 0002 / TRAP 000C
=======================================================
SYSTEMS MAY LOCKUP WITH A 110 ERROR, TRAP 0002 ERROR,
TRAP 000C ERROR, OR AN NMI INTERMITTENT.
THESE ERRORS MAY OCCUR IF AN OPERATING SYSTEM DETECTS A
MEMORY ERROR.
HIGHLY INTERMITTENT MEMORY ERRORS CAN ESCAPE DETECTION BY
DIAGNOSTICS IF NO FAILURE ACTUALLY OCCURS DURING THE TEST.
MEMORY INTENSIVE OPERATING SYSTEMS, SUCH AS OS/2, AIX AND OTHERS
ARE CAPABLE OF REVEALING HIGHLY INTERMITTENT MEMORY BIT FAILURES
WHICH DIAGNOSTICS MAY NOT REVEAL.
MEMORY FAILURES UNDER DOS COULD DISPLAY A 110 MEMORY FAILURE,
WHILE FAILURES RUNNING UNDER OS/2 COULD DISPLAY A TRAP 0002
OR A TRAP 000C ERROR MESSAGE. AIX WILL GIVE AN NMI ERROR.
THE OS/2 ERROR MESSAGE WILL INFORM THE USER THAT THE OPERATING
SYSTEM HAS DETECTED A HARDWARE MEMORY ERROR ON THE SYSTEM BOARD
OR THE CHANNEL. THE INFORMATION DISPLAYED ON THE SCREEN BY
OS/2 DOES NOT CORRELATE TO AN ACTUAL FAILING MEMORY MODULE.
THE DATA DISPLAYED BY OS/2 IS INVALID FOR HARDWARE PROBLEM
DETERMINATION, BUT IS MEANINGFUL FOR SOME TYPES OF SOFTWARE
TRAP PROBLEM DETERMINATION.
TRAP 000D (TRAP000D) ERRORS ARE USUALLY RELATED TO SOFTWARE
PROBLEMS AND MAY BE CAUSED BY SEVERAL DIFFERENT PROGRAMMING
ERRORS. OS/2 SOFTWARE SUPPORT SHOULD BE CONSULTED FOR
TRAP 000D ERRORS.
THE MOST COMMON TYPE OF TRAP 0002 ERROR IS CAUSED BY MEMORY,
BUT IT MAY ON RARE OCCASIONS BE CAUSED BY A SYSTEM BOARD
FAILURE. (IF THE SYSTEM BOARD DIAGNOSTICS RUN ERROR-FREE, THE
CHANCES OF IT BEING DEFECTIVE ARE REMOTE.)
THE MOST EFFECTIVE TROUBLESHOOTING METHOD FOR THIS PROBLEM IS
TO REPLACE THE SYSTEM MEMORY, STARTING WITH THE MEMORY ON THE
SYSTEM BOARD. IF THE ERROR REMAINS, CONTINUE THE REPLACEMENT
PROCESS WITH THE MEMORY EXPANSION SIMS UNTIL THE FAILURE NO
LONGER OCCURS.
THE MEMORY DIAGNOSTIC WAS REVISED AND IMPROVED ON THE FOLLOWING
LEVELS OF SYSTEM REFERENCE DISKETTES:
+++++++++++++++++++++++++++++++++++++++++++++
8570/8580 REFERENCE DISKETTE VERSION 1.10
8550/8560 REFERENCE DISKETTE VERSION 1.04
8555/8565 REFERENCE DISKETTE VERSION 1.03
+++++++++++++++++++++++++++++++++++++++++++++
HIGHLY INTERMITTENT ERRORS MAY GO UNDETECTED BY ANY MEMORY
DIAGNOSTIC. MULTIPLE REPLACEMENTS MAY BE NECESSARY TO ISOLATE
THE FAILURE IN EXTREME CASES.
SYSTEMS WHICH HAVE THE ENHANCED 80386 MEMORY EXPANSION ADAPTER
INSTALLED (FRU P/N34F2825) MAY ALSO EXPERIENCE OS/2 TRAP ERRORS
IF THE ENHANCED 80386 MEMORY ADAPTER DOES NOT HAVE RESISTORS
LOCATED DIAGONALLY ACROSS THE MODULES LOCATED IN POSITIONS U21,
U22, U23, AND U24. RETAIN RECORD # HO37481 SHOULD BE REFERENCED
FOR ADDITIONAL DETAILS.
~~~~~~~~
Title: PS/2 Heat & power specs 1002
SYSTEM < heat output > Max Current - 240V range
BTU Watts Draw (Amps)
PS/2 Mod 30 341 100 -
PS/2 Mod 30-286 438 129 -
PS/2 Mod 50 494 145 1.4
PS/2 Mod 55SX 476 140 1.3
PS/2 Mod 60 1240 364 2.7
PS/2 Mod 65SX 1218 358 2.7
PS/2 Mod 70 748 220 3.0
PS/2 Mod P70 510 150 2.0
PS/2 Mod 80 1245 365 265
PS/2 Mod 80(SCSI) 1390 409 -
8503 188 55
8512 208 61
8513 273 80
8514 307 90
8515 341 100
~~~~~~~~